home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
misc
/
merit
/
noop
/
ietf.min
< prev
next >
Wrap
Text File
|
1991-03-21
|
9KB
|
252 lines
Network OSI Operational Working Group
Minutes
March 12, 1991
St. Louis
Chair:
Sue Hares/Merit (skh@merit.edu)
Mailing List:
noop-request@merit.edu (administrative requests only)
noop@merit.edu
Minutes:
The meeting minutes were submitted by Richard Colella (NIST).
Editor of Minutes: Sue Hares
+---------------+
| Introductions |
+---------------+
The first meeting of the Network OSI Operational (NOOP) Working Group
was opened by the Chair, Sue Hares (Merit). A minute-taker was
selected, introductions were made, and the agenda was presented and
approved as presented.
+---------+
| Charter |
+---------+
Sue presented the NOOP WG proposed charter for discussion. It was
agreed that an additional category be added to the areas for
publication, that of tutorials on OSI relevant to the WG's
activities. Several of these were identified immediately:
* DIS 10589 - Ross Callon (DEC) agreed to find or write a
tutorial on DIS 10589, the IS-IS Intra-domain Routing
protocol;
* IDRP - Dave Katz (Merit) will write a tutorial on the
Inter-domain Routing Protocol, currently under
consideration in ANSI and ISO; and,
* CLNP and ES-IS - Rob Hagens (U. Wisc) will allow us
to post two tutorial articles he's written, and
previously published in Connexions on CLNP and ES-IS.
+---------------+
| Routing Plans |
+---------------+
Tutorial on OSI NSAP Guidelines
-------------------------------
As an introduction to the discussion of routing plans, Ross presented
a tutorial on the Internet Draft document, "Guidelines for OSI NSAP
Allocation in the Internet" (Colella, Gardner, Callon). The slides
will be included in the proceedings.
Five Questions about NSAPs
--------------------------
Sue addressed the five most-often asked questions about NSAPs:
1) How does one get NSAPs outside the US?
The authority for NSAP allocation under the Data Country
Code (DCC) is assigned by ISO to the ISO Member Body (MB)
from each country. In the US, for example, this is ANSI;
in the UK it is the British Standards Institute. Each MB
is responsible for administering (or delegating the adminis-
tration of) NSAPs under its DCC.
Alternatively, one could approach an organization that has
obtained an International Code Designator (ICD), which are
not country-based.
2) What happens when you change regionals?
If your NSAP addresses are taken from a regional's address
space and you change regionals, your addresses will need
to change. This is a consequence of using hierarchical
addressing.
Auto-configuration of ES NSAPs will help this, but there is
not standard on this to date (but see below).
X.500 must be capable of supporting this transition. Since
the primary source of addressing information for communicants
will be acquired through X.500, X.500 must have mechanisms
to support wholesale changes of NSAPs.
3) What is the state of auto-configuration of NSAPs?
Today, some vendors use the ES-IS HELLO PDU to construct ES
NSAPs. The ES listens for a HELLO when it is booted, and
uses the area address of the IS for its area address. The
ES uses its own IEEE MAC address in the system ID field of
the NSAP.
There is a new work item in ANSI X3S3.3 for support of address
transition. The proposed mechanism is to use IS-IS flooding
and ES-IS to distribute new NSAP information within and area.
Note that this does not obviate the need for some support from
X.500 as discussed in the previous question.
4) Quality of Service (QoS) -- what about it?
QoS is also known by other names, such as Type of Service (ToS)
and policy. This is considered a research issue (and is for
further study by someone else).
5) How does a company transition between two different
OSI NSAPs?
It was decide this question was simply way of
asking question 2.
Sample Routing Plans
--------------------
There was general agreement on several points:
* Regionals and Backbones should each obtain an AA from GSA or
an ORG ID from ANSI and allocate addresses to their clients
based on these (Richard agreed to distribute information on
how to obtain an AA to the WG mailing list).
* Multiply-homed clients (e.g., campuses) should use addresses
taken from the address of their primary point of attachment.
* For administrative reasons, a regional *could* further subdivide
the RD field. For example, MIDNET clients are organized along
state boundaries. The first nibble of the RD field could be
used as a state identifier, with the other 12 bits managed by
the state. It was decided that this is not a good idea:
- each additional subdivision wastes address space, so this
should only be done when absolutely necessary,
- does not provide a significant added value to the state
(new RDs are not needed that often),
- it may cause confusion because current administrative fields
in the NSAP DSP (i.e., AA, RD, and Area) are being used
synonymously with topological routing structures, and these
bits are *not*, and,
- it's really just as easy for the regional to manage a flat
RD space.
Seven people agreed to write routing plans and submit them for
distribution to the WG. These plans can be used as the basis for
discussion of issues that arise and as examples for others who are
contemplating developing NSAP addressing and routing plans. No
specific dates were set, but the following lists those who agreed to
contribute a plan:
* CICNET -- Linda Winkler (Argonne National Lab)
* ESNET -- Tony Hain (Lawrence Livermore National Lab)
* MIDNET -- Dale Finkelson (MIDNET)
* Mitre -- Walt Lazear (Mitre)
* NSFNET -- Dave Katz (Merit)
* OARNET -- Kannan Varadhan (Ohio Academic Resource Network)
* Westnet -- Carol Ward (University of Colorado)
+-------+
| Tools |
+-------+
As in the operational IP networks, there is a need for OSI tools
to support network operation and debugging. Sue broke this up
into a number of separate areas.
Utilities
---------
Various OSI-based utilities are needed. Some are available and
some are not. These need to be identified and implemented. The
slides identified a number of utilities. Note that network
management is not of immediate concern to the WG, but CMIP-based
NM is anticipated.
[Editor's note: The text of the slides will be sent to the mail group.
The basic utilities needed were:
- ISO versions of ping (ISO echo RFC 1139),
- ISO version of traceroute (using ISO ping as packet sent)
- method to display ISO routes
- method to display ES-IS cache ]
Making NM Monitors
------------------
Utilities such as ISO ping can be combined to create Network Management
Monitors. Sue Hares will send a write up of a simple network management
monitor to the mailing list.
NOC Tools 2
-----------
This working group will collect information on OSI tools.
A document point to OSI utilities in either the NOC tools RFC will
be written. Please send information about OSI utilties to
noop@merit.edu.
Router and Host Survey Documents
--------------------------------
It would be useful to have a pair of documents that survey OSI
software availability, one each for hosts and routers. Emphasis
is on those tools that are needed to run an operational network.
Everyone is asked to contribute material to this effort. Again
send information to noop@merit.edu.
+-------------------------+
| Summary of Action Items |
+-------------------------+
This section contains a summary of action items from the St. Louis
meeting.
* DIS 10589 tutorial -- Ross Callon
* IDRP tutorial -- Dave Katz
* CLNP and ES-IS tutorials -- Rob Hagens
* Info on obtaining a GOSIP AA -- Richard Colella
* CICNET routing plan -- Linda Winkler
* ESNET routing plan -- Tony Hain
* MIDNET routing plan -- Dale Finkelson
* Mitre routing plan -- Walt Lazear
* NSFNET routing plan -- Dave Katz
* OARNET routing plan -- Kannan Varadhan
* Westnet routing plan -- Carol Ward
* Router and Host survey information -- all
* write-up on simple ISO pingky monitor - Sue Hares